Multi-Mode IVR

ABSTRACT

Included are embodiments of systems and methods for providing information. At least one embodiment of such a method includes facilitating establishment of a communication between a user on a communications device and an interface server, the interface server being configured to provide data related to an information tree to the user, the information tree being configured with a plurality of options. Some embodiments include facilitating navigation of a user through the information tree and receiving a first version of a marker from the user, the marker being configured to mark at least one position in the information tree. Still some embodiments include associating the received first version of the marker with a position in the information tree.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of copending U.S. utility applicationentitled, “Multi-Mode IVR,” having Ser. No. 11/627,209, filed Jan. 25,2007, which is entirely incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates to a multi-mode Interactive Voice Response (IVR)session.

BACKGROUND

Users often desire customer service and/or otherwise place calls thatresult in interaction with an Interactive Voice Response (IVR) system.During an IVR session, the IVR may present the user with options fornavigating to the desired destination. As a nonlimiting example, theuser may input an address (e.g., dial a telephone number, enter anInternet Protocol (IP) address, etc.) that is associated with an IVR.Upon connection of a communication session with the IVR, the IVR maypresent the user with a plurality of options. Depending on theparticular configuration, the user may respond to the provided optionswith a Dial-Tone Multi-Frequency (DTMF) input, a voice input and/orother input. The IVR may continue to provide subsequent options to theuser, based on the received user input, until a desired destination isachieved.

While many IVRs are configured to provide users with desiredinformation, oftentimes a user is disconnected from the IVR prior toreceiving the desired information or reaching the desired destination.Additionally, users may select one or more options that do notcorrespond to the desired destination. When such a scenario occurs, theuser must return to the first options of the IVR and begin the processagain.

Thus, a heretofore unaddressed need exists in the industry to addressthe aforementioned deficiencies and inadequacies.

SUMMARY

Included are embodiments of systems and methods for providinginformation. At least one embodiment of such a method includesfacilitating establishment of a communication between a user on at leastone communications device and an interface server, the interface serverbeing configured to provide data related to an information tree to theuser, the information tree being configured with a plurality of options.Some embodiments include facilitating navigation of a user through theinformation tree and receiving a first version of a marker from theuser, the marker being configured to mark at least one position in theinformation tree. Still some embodiments include associating thereceived first version of the marker with a position in the informationtree.

Also included are embodiments of a computer readable medium. At leastone embodiment includes first facilitating logic configured tofacilitate establishment of a communication between a user on at leastone communications device and an interface server, the interface serverbeing configured to provide data related to an information tree to theuser, the information tree being configured with a plurality of options.Some embodiments include second facilitating logic configured tofacilitate navigation of a user through the information tree and firstreceiving logic configured to receive a first version of a marker fromthe user, the marker being configured to mark at least one position inthe information tree. Still some embodiments include associating logicconfigured to associate the received first version of the marker with aposition in the information tree.

Other systems, methods, features, and/or advantages of this disclosurewill be or may become apparent to one with skill in the art uponexamination of the following drawings and detailed description. It isintended that all such additional systems, methods, features, andadvantages be included within this description and be within the scopeof the present disclosure.

BRIEF DESCRIPTION

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views. While several embodiments are described inconnection with these drawings, there is no intent to limit thedisclosure to the embodiment or embodiments disclosed herein. On thecontrary, the intent is to cover all alternatives, modifications, andequivalents.

FIG. 1 is a diagram illustrating an exemplary embodiment of a networkconfiguration for providing users with information.

FIG. 2 is a diagram illustrating an exemplary embodiment of a networkconfiguration with a plurality of interface servers, similar to thediagram from FIG. 1.

FIG. 3 is a diagram illustrating an exemplary embodiment of componentsthat may be present in an interface server, such as the interface serverfrom FIG. 2.

FIG. 4 is a diagram illustrating an exemplary embodiment of options thatmay be provided to a user upon the establishment of a communicationssession with an interface server, such as the interface server from FIG.3.

FIG. 5 is a diagram of a user interface that may be presented to a userthat interacts with an interface server, such as the interface serverfrom FIG. 3.

FIG. 6 is a diagram illustrating a user interface that may facilitatestorage and/or location of an IVR marker, similar to the interface fromFIG. 5.

FIG. 7 is a diagram illustrating a user interface that may facilitatemarking of a place in an IVR session, similar to the diagram from FIG.6.

FIG. 8 is a diagram illustrating a user interface that may facilitateresumption of an IVR session, similar to the interface from FIG. 7.

FIG. 9 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for navigating an IVR, such as may be provided bythe interface server from FIG. 4.

FIG. 10 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for creating a marker for an IVR, similar to theflowchart from FIG. 9.

FIG. 11 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for resuming an IVR session, similar to theflowchart from FIG. 10.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a processfor receiving a command and command assignment for implementation in anIVR session, similar to the flowchart from FIG. 11.

FIG. 13 is a flowchart illustrating an exemplary embodiment of a processfor utilizing a command and command assignment in an IVR session,similar to the flowchart from FIG. 12.

FIG. 14 is a flowchart illustrating an exemplary embodiment of a processfor returning a user to a desired point in an IVR menu, similar to theflowchart from FIG. 13.

FIG. 15 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to provide an IVR session to a user, similar tothe flowchart from FIG. 14.

FIG. 16A is a flowchart illustrating an exemplary embodiment of aprocess for an interface server to record a user position during an IVRsession, similar to the flowchart from FIG. 15.

FIG. 16B is a continuation of the flowchart from FIG. 16A.

FIG. 17 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to receiving a command and command assignment,similar to the flowchart from FIGS. 16A and 16B.

FIG. 18 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to execute a desired command according to acommand assignment, similar to the flowchart from FIG. 19.

FIG. 19 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to return a user to a desired point in an IVR,similar to the flowchart from FIG. 18.

FIG. 20A is a sequence diagram illustrating an exemplary embodiment of aprocess for providing a setting for an IVR, such as may be provided bythe interface server from FIG. 3.

FIG. 20B is a continuation of the sequence diagram from FIG. 20A.

DETAILED DESCRIPTION

Embodiments of this disclosure add rich media features to InteractiveVoice Response (IVR) systems by incorporating protocols such as Voiceover Internet Protocol (VoIP) for cross-mode digital interaction.Additionally, messaging and user interface improvements based on MotionPicture Experts Group-3 (MPEG3) and/or MPEG4 allow aural and otherthumbnails and markers for marking specific locations in an informationtree of the IVR. Additionally, some embodiments include video enhancedcollaborative interaction among locations in the information tree. Someembodiments may include media enhanced programmable buttons to controlthese features. These embodiments may be configured, whereby specificmedia components such as photos and/or videos can be shown in real timeon a button (or other option) that corresponds to the locations and/orspecific features available at a location in the information tree. As anonlimiting example, a user interface associated with an IVR may displaya photo of Grandma and a BellSouth® logo, indicating where Grandma canaccess her BellSouth® accounts from her cellular telephone. By selectingthe photo, Grandma may be presented with her account information.

Additionally, at least one embodiment may be configured with a userdevice, where the user can assign a type of marker (e.g., assign acertain key sequence, music, picture, etc.) such that if the user isdisconnected from the IVR (and/or navigates to an undesired location inthe information tree of the IVR), the user can return to a desiredlocation in the IVR by inputting the marker to the device. The devicemay also be configured to navigate the IVR to the desired location inthe information tree.

Similarly, at least one embodiment includes a network that may beconfigured to receive an identifier, a marker, and/or other indicationto document a user's navigation through the IVR. If the user isdisconnected from the IVR, the data related to the navigation may beavailable to the user (with the same or different user device) when theuser returns. This can provide a configuration where, when the userreturns, the user can automatically return to a predetermined place inthe IVR. In this embodiment, the network may also be configured to storethe navigation, as well as the marker to determine the user's desireddestination.

FIG. 1 is a diagram illustrating an exemplary embodiment of a networkconfiguration for providing users with information. As illustrated, aplurality of users may be connected via an external network such as acommunications network 100. The communications network 100 can include,for example, the Internet, a Wi-Fi® network (IEEE 802.11 compatible), aWi-Max network (IEEE 802.16 compatible), a Public Switched TelephoneNetwork (PSTN), a cellular communications network, the Internet, and/orother communications mediums. Users may access the communicationsnetwork 100 via a communications device 102, a communications device104, and/or a communications device 106 (via a wireless access point108).

It should be appreciated that the network 100, the communicationsdevices 102, 104, 106 (via the wireless access point 108), andconnections illustrated in FIG. 1 are shown by way of example and arenot intended to limit this disclosure. This disclosure may be applicableto any communications device, connection, and network that supportsvoice, data, and/or other types of communications.

One should note that depending on the type of communication desired,different functionality may be utilized. More specifically, while thecommunications devices 102 and 106 may be configured to facilitate voicecommunications over a cellular network and/or a PSTN, these devices mayalso be configured for data communications via the Internet. Similarly,the communications devices 102 and 106 may also be configured tofacilitate communications via a Wi-Fi® network and/or a Wi-Max network.As a nonlimiting example, if a user operating the communications device106 wishes to make a cellular communication, the user can input theaddress (e.g., telephone number) of the called party device. Thisaddress can be sent to the wireless access point 108 (which may includea cellular antenna and/or other component), configured to send thecommunication request to the network 100. The network 100 may employ oneor more cellular networks, PSTNs and/or other networks for facilitatingthe communication. Upon connecting the communications device 104 with acalled party device, such as with the communications device 102,communication may begin.

Similarly, if a user operating the communications device 104 wishes toaccess a website (and/or other data associated with the Internet), theuser can send a communication request, which may include an address,such as a Uniform Resource Locator (URL) or other Uniform ResourceIdentifier (URI). The request can be sent to the desired computingdevice (such as a server data storage) via the network 100, which mayinclude the Internet, a Wi-Max network a Wi-Fi® network, cellularnetwork, and/or other network. The desired computing device can thenrespond by sending the requested data to the communications device 104via the same (or similar) transmission mediums.

Also included in the nonlimiting example of FIG. 1 is a voicemail server110. The voicemail server 110 may be configured to serve one or moreuser accounts. More specifically, in at least one embodiment, thevoicemail server 110 may be configured to provide voicemail services fora telephone line coupled to the communications device 102. The voicemailserver 110 may be configured to receive a redirected call intended for auser associated with the communications device 102. If the network 100determines that a user is currently not available on the communicationsdevice 102, the call may be redirected to the voicemail server 110.Similar to interface servers 218 a-218 c (FIG. 2), the voicemail server110 may be configured to provide the caller with an IVR for providingoptions for leaving a message.

FIG. 2 is a diagram illustrating an exemplary embodiment of a networkconfiguration with a plurality of interface servers, similar to thediagram from FIG. 1. As illustrated in the nonlimiting example of FIG.2, a PSTN configured a communications device, such as the communicationsdevice 102 may be coupled to a PSTN 202. Also coupled to the PSTN 202 isthe Interface server 218 a. The interface server 218 a may be a PSTNbased server and may be configured to provide an information tree to auser. More specifically, in response to a user dialing a predeterminedaddress associated with the interface server 218 a, a user may establisha communications session with the interface server 218 a. The interfaceserver 218 a may be configured to provide an automated Interactive VoiceResponse (IVR) interface to the user. The IVR may be configured toprovide an information tree of options for the user to quickly reach adesired portion of the IVR interface.

As a nonlimiting example, a user may call a BellSouth® directory numberlooking for information related to starting new Direct Service Line(DSL) service. In response to establishing a communications session withthe BellSouth® interface server 218 a, the interface server 218 a canprovide the user with an option to view a current bill, an option toreceive technical support, an option for employment opportunities and anoption to start new service. Upon selecting the option to start newservice, the IVR may provide the user with an option to start newdial-up service, an option for DSL service and an option for Very HighBit Rate DSL (VDSL) service. Upon selection of the second option, theuser may then be provided with the desired information.

Also included in the nonlimiting example of FIG. 2, is an InternetProtocol (IP) network configured communications device, such as thecommunications device 104. The IP network configured communicationsdevice 104 may be configured to communicate via an IP network 204, whichmay utilize VoIP protocols and/or other IP protocols. Also coupled tothe IP network 204 is the IP configured interface server 218 b, whichmay be configured to provide similar functionality as the PSTN basedinterface server 218 a in an IP environment. The IP network 204 is alsocoupled to the PSTN 202 and a wireless network 206.

The wireless network 206 is coupled to one or more of the wirelessaccess points 108, which may operate on a wireless cellular protocol, onan IEEE 802.11 or other wireless protocol to communicate with a wirelessconfigured communications device, such as the communications device 106and/or the wireless configured interface server 218 c.

FIG. 3 is a diagram illustrating an exemplary embodiment of componentsthat may be present in an interface server 218, such as the interfaceservers 218 a-218 c from FIG. 2. Although a wire-line communicationsdevice is illustrated, this discussion can be applied to wirelessdevices, as well. Generally, in terms of hardware architecture, as shownin FIG. 3, the interface server 218 includes a processor 382, volatileand nonvolatile memory 384, a display interface 394, data storage 395,one or more input and/or output (I/O) device interface(s) 396, and/orone or more network interfaces 398 that are communicatively coupled viaa local interface 392. The local interface 392 can include, for examplebut not limited to, one or more buses or other wired or wirelessconnections. The local interface 392 may have additional elements, whichare omitted for simplicity, such as controllers, buffers (caches),drivers, repeaters, and receivers to enable communications. Further, thelocal interface 392 may include address, control, and/or dataconnections to enable appropriate communications among theaforementioned components. The processor 382 may be a device forexecuting software, particularly software stored in the volatile andnonvolatile memory 384. The processor 382 can include any custom made orcommercially available processor, a central processing unit (CPU), anauxiliary processor among several processors associated with theinterface server 218, a semiconductor based microprocessor (in the formof a microchip or chip set), a macroprocessor, and/or generally anydevice for executing software instructions.

The memory 384 can include any one or combination of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape,CDROM, etc.). Moreover, the memory 384 may incorporate electronic,magnetic, optical, and/or other types of storage media. One should notethat the memory 384 can have a distributed architecture (where variouscomponents are situated remote from one another), but can be accessed bythe processor 382.

The software in the volatile and nonvolatile memory 384 may include oneor more separate programs, each of which includes an ordered listing ofexecutable instructions for implementing logical functions. In theexample of FIG. 3, the software in the volatile and nonvolatile memory384 may include IVR logic 399, as well as an operating system 386. Theoperating system 386 may be configured to control the execution of othercomputer programs and provide scheduling, input-output control, file anddata management, memory management, and communication control andrelated services.

A system component and/or module embodied as software may also beconstrued as a source program, executable program (object code), script,or any other entity comprising a set of instructions to be performed.When constructed as a source program, the program is translated via acompiler, assembler, interpreter, or the like, which may or may not beincluded within the volatile and nonvolatile memory 384, so as tooperate properly in connection with the operating system 386.

The Input/Output devices that may be coupled to system I/O Interface(s)396 may include input devices, for example but not limited to, akeyboard, mouse, scanner, microphone, etc. Further, the Input/Outputdevices may also include output devices, for example but not limited to,a printer, display, speaker, etc. Finally, the Input/Output devices mayfurther include devices that communicate both as inputs and outputs, forinstance but not limited to, a modulator/demodulator (modem; foraccessing another device, system, or network), a radio frequency (RF) orother transceiver, a telephonic interface, a bridge, a router, etc.

Additionally included are the one or more network interfaces 398 forfacilitating communication with one or more other devices. Morespecifically, the network interface 398 may include any componentconfigured to facilitate a connection with another device. While in someembodiments, among others, the interface server 218 can include thenetwork interface 398 that includes a Personal Computer Memory CardInternational Association (PCMCIA) card (also abbreviated as “PC card”)for receiving a wireless network card, however this is a nonlimitingexample. Other configurations can include the communications hardwarewithin the computing device, such that a wireless network card isunnecessary for communicating wirelessly. Similarly, other embodimentsinclude the network interfaces 398 for communicating via a wiredconnection. Such interfaces may be configured with Universal Serial Bus(USB) interfaces, serial ports, and/or other interfaces.

If the interface server 218 includes a personal computer, workstation,or the like, the software in the volatile and nonvolatile memory 384 mayfurther include a basic input output system (BIOS) (omitted forsimplicity). The BIOS is a set of software routines that initialize andtest hardware at startup, start the operating system 386, and supportthe transfer of data among the hardware devices. The BIOS is stored inROM so that the BIOS can be executed when the communications device 106is activated.

When the interface server 218 is in operation, the processor 382 may beconfigured to execute software stored within the volatile andnonvolatile memory 384, to communicate data to and from the volatile andnonvolatile memory 384, and to generally control operations of thecommunications device 106 pursuant to the software. Software in memory,in whole or in part, may be read by the processor 382, perhaps bufferedwithin the processor 382, and then executed.

One should note that while the description with respect to FIG. 3includes the interface server 218 as a single component, this is anonlimiting example. More specifically, in at least one embodiment, theinterface server 218 can include a plurality of servers, personalcomputers, and/or other devices. Similarly, while the description ofFIG. 3 describes the interface server 218, this is also a nonlimitingexample, as other components may also be included in this description,such as SIP locator and/or other components.

Additionally, while the IVR logic 399 is illustrated in FIG. 3 as asingle software component, this is also a nonlimiting example. In atleast one embodiment, the IVR logic 399 may include one or morecomponents, embodied in software, hardware, and/or firmware.Additionally, while the IVR logic 399 is depicted as residing on asingle computing device, as the interface server 218 may include one ormore devices, the IVR logic 399 may include one or more componentsresiding on one or more different devices.

The embodiments disclosed herein can be implemented in hardware,software, firmware, or a combination thereof. At least one embodimentdisclosed herein is implemented in software and/or firmware that isstored in a memory and that is executed by a suitable instructionexecution system. If implemented in hardware, as in an alternativeembodiment, embodiments disclosed herein can be implemented with any ora combination of the following technologies: a discrete logic circuit(s)having logic gates for implementing logic functions upon data signals,an application specific integrated circuit (ASIC) having appropriatecombinational logic gates, a programmable gate array(s) (PGA), a fieldprogrammable gate array (FPGA), etc.

FIG. 4 is a diagram illustrating an exemplary embodiment of options thatmay be provided to a user upon the establishment of a communicationssession with an interface server, such as the interface server 218 fromFIG. 3. As illustrated in the nonlimiting example of FIG. 4, theinterface server 218 may be configured to provide an information treefor providing information to a user. More specifically, uponestablishing a communications session with the interface server 218, auser may be provided with the first tier of options. A first option mayindicate that by pressing “1,” the user can be provided with hardwareoptions. A second option may indicate that by pressing “2,” the user maybe provided with sporting goods options. A third option may indicatethat by pressing “3,” the user may be provided with bedding options. Afifth option may indicate that by pressing “5,” the user may be providedwith electronics options. A sixth option may indicate that by pressing“6,” the user may be provided with clothing options. A seventh optionmay indicate that by pressing “0,” the user may be connected with arepresentative.

In response to selection of the second option, the user may be presentedwith a plurality of second tier options. More specifically, a firstsecond tier option may indicate that by pressing “1,” the user may beprovided with basketball options. A second second tier option mayindicate that by pressing “2,” the user may be provided with footballoptions. A third second tier option may indicate that by pressing “3,”the user may be presented with golf options. A fourth second tier optionmay indicate that by pressing “4,” the user may be presented withrunning options. A fifth second tier option may indicate that bypressing “0” the user may be connected with a representative.

In response to selection of the third second tier option, the user maybe presented with a plurality of third tier options. More specifically,a first third tier option may indicate that by pressing “1,” the usermay be presented with apparel options. A second third tier option mayindicate that by pressing “2,” the user is presented with clubs options.A third third tier option may indicate that by pressing “3,” the user ispresented with shoes options. A fourth third tier option may indicatethat by pressing “0,” the user may be connected with a representative.

As illustrated, the user may navigate numerous tiers of options beforereaching the desired information. As such, if the user is disconnectedwith the IVR or selects an undesirable option, oftentimes the user willbe forced to restart from the first tier of options.

One should note that the options provided in the information treedepicted in FIG. 4 are merely a nonlimiting example. Additionally,depending on the particular configuration, the information tree may bepresented as an audio presentation of options and/or a visualpresentation of options. Further, while only one set of second tieroptions and one set of third tier options are illustrated in FIG. 4,this is also a nonlimiting example, as one or more of the first tieroptions may have corresponding second tier options, third tier options,fourth tier options, etc.

FIG. 5 is a diagram of a user interface that may be presented to a userthat interacts with an interface server, such as the interface server218 from FIG. 3. More specifically, as illustrated in the nonlimitingexample of FIG. 5, a communication interface 520 may be presented to auser via one or more of the communications devices 102, 104, 106, and/orother communications device. Included in the communication interface 520is a display window 522 for presenting images, video, and/or filesassociated with an established communications session. According to atleast one exemplary embodiment, displayed in data section 526 are dataassociated with the one or more other parties that are associated withthe current communications session, a duration of the communicationsession, a current position in the information tree, and a date of aprevious communications session. Additionally included in thisnonlimiting example is a duration of the previous communicationssession, a position in the information tree during the previouscommunications session, and an indication of whether the previous datawas saved at the communications device 102, 104, 106 and/or at theinterface server 218. Also included are a transcript section 524, a sentsection 528, and a received section 530. According to at least oneexemplary embodiment, in the transcript section 524 is a transcript ofthe options presented by the IVR as well as data associated with theuser's selections. In the sent section 528 is an indication of dataand/or files sent to the IVR. In the received section 530 is datareceived from the IVR.

Also included in the nonlimiting example of FIG. 5 is a hang up option532, a capture option 534, a take me option 536, and a mark option 538.More specifically, the hang up option 532 may be configured todisconnect the current communications session. The capture option 534may be configured to capture potential markers, as discussed in moredetail below. The take me option 536 may be configured to resume aprevious communications session with the IVR, as discussed in moredetail below. The mark option 538 may be configured to mark a currentcommunications session for future retrieval.

FIG. 6 is a diagram illustrating a user interface that may facilitatestorage and/or location of an IVR marker, similar to the interface 520from FIG. 5. As illustrated in the nonlimiting example of FIG. 6,communication interface 620 may include options that may be accessiblein response to a user selection of the capture option 534. Morespecifically, in at least one embodiment, the user can capture an imageby selecting image capture option 622. In operation, a user can capturean image via a camera or other image capture device, and/or viacapturing a screenshot by a local operating system and/or other localapplication. Similarly, by selecting a find option 624, the user canlocate a previously captured image that may be stored locally and/orremotely from the communications device 102, 104, 106. Also included inthe nonlimiting example of FIG. 6 is an audio capture option 626. Theaudio capture option 626 can facilitate recording of audio data for useas a marker. An audio find option 628 can be selected for findingpreviously captured audio data. A video capture option 630 may beutilized for capturing video data. A video find option 632 may beutilized for finding previously captured video data. A go back option634 can return the user to the user interface 520 from FIG. 5.

One should also note that while capture and/or location of image data,audio data, control data, and/or video data may be facilitated via agraphical user interface (GUI), this is a nonlimiting example. Morespecifically, in at least one exemplary embodiment a user may bepresented with these options in an audio exchange with thecommunications device 102, 104, 106.

FIG. 7 is a diagram illustrating a user interface that may facilitatemarking of a place in an IVR session, similar to the diagram from FIG.6. As illustrated in the nonlimiting example of FIG. 7, in response toselection of the mark option 538, the user may be presented with acommunication interface 720. More specifically, a user can mark acurrent position in an information tree (e.g., see FIG. 4) that ispresented as part of an IVR. The user can select the desired marker(which may include a sound, image, video, etc.) by entering a mark name(and/or location) in a “mark current position” option 722. By selectingthe “mark current position” option 722, the user's current position inan information tree may be stored and associated with the select mark.The user can return to the interface from FIG. 5 upon selection of a goback option 724.

As discussed above, while in some embodiments, a user may utilize agraphical user interface for marking a current position in aninformation tree, these are nonlimiting examples. More specifically, inat least one exemplary embodiment, no interface need be provided formarking a current location in an information tree. If a user isnavigating the information tree, the user may provide the previouslystored marker to the communications device 102, 104, 106. Depending onthe particular configuration, the communications device 102, 104, 106and/or the interface server 218 may store the marked position in theinformation tree.

More specifically, as an additional nonlimiting example, if the user hascreated an audio marker that includes the user's voice saying “take mehome,” the user can simply say the phrase “take me home” for marking thecurrent position, without being prompted. If the user says the phrase“take me home” again, the user may return to the marked position (inthis communication session or in another).

One should also note that, referring back to FIG. 4, a user may bepresented with a graphical representation of the information tree. In atleast one embodiment, an icon may be displayed on that interface toillustrate the user's current position in the information tree. The usermay also be provided options to insert a marker as audio data, imagedata, control data, and/or video data at one or more locations in theinformation tree. By inserting a marker on the interface, the user canmark this position such that if the user wishes to return to thisposition at a later time, the user may simply “click,” say, and/orotherwise provide the marker being displayed.

More specifically, as a nonlimiting example, If the marker is associatedwith audio data, the user can return to the marked position by repeatingthe audio data (by voice, recording, etc.) to the communications device102, 104, 106 (and/or to the interface server 218).

FIG. 8 is a diagram illustrating a user interface that may facilitateresumption of an IVR session, similar to the interface 720 from FIG. 7.As illustrated in the nonlimiting example of FIG. 8, a communicationinterface 820 may be presented to a user in response to selection of thetake me option 536 (FIG. 5). The communication interface 820 may includeone or more options for taking the user to a desired point in aninformation tree. More specifically, the interface 820 includes aposition of last visit option 822, which may be configured to return theuser to the last position reached during the user's last visit to theinformation tree. Additionally included is an up one level option 824for taking the user to a previous tier in the information tree (e.g.,from a current position at tier 2 to a position in tier 1). An up twolevels option 826 may be configured to take the user up two tiers fromthe current tier in the information tree. An up to beginning option 828may be configured for returning the user to the beginning of theinformation tree. A “to last saved place” option 830 may also beincluded and configured to return the user to the last place in theinformation tree that was marked by the user. A go back option 832 maybe configured to return the user to the interface 520 from FIG. 5.

One should note that while options associated with the information treemay be presented in a user interface, such as the interface from FIG. 8,this is a nonlimiting example. More specifically, in at least oneexemplary embodiment, a user of the communications device 102, 104, 106may be configured to receive a predetermined aural thumbnail for one ormore of the options in FIG. 8. As a nonlimiting example, a predeterminedaural thumbnail for taking the user to the position of last visit mayhave been set to audio data associated with “The Star Spangled Banner.”The aural thumbnail may be presented to the communications device 102,104, 106 via the user's voice, a recording, and/or other techniques forpresentation of the aural thumbnail. Upon receipt of the desired audiodata, the communications device 102, 104, 106 can retrieve dataassociated with the previous visit to navigate the information tree tothe desired position.

Additionally included in exemplary embodiments described herein areconfigurations for facilitating the creation of a command and/or commandassignment for performing actions with an IVR. More specifically, as anonlimiting example, the communications device 102, 104, 106 may beconfigured to receive a command from a user. The command may include anaudio command, a video command, a DTMF command, an image command, and/orother command. The communications device 102, 104, 106 (and/or theinterface server 218) may then determine a command assignment to desiredinterface action. This data can be stored such that when thecommunications device 102, 104, 106 receives the command, the receivedcommand can be used to determine the desired interface action.

More specifically, as an additional nonlimiting example, if a userselects a key sequence to represent a command to automatically connectwith a representative (e.g., bypassing the IVR), the user may create acommand (e.g., the desired key sequence) and a command assignment (e.g.,the desired outcome). A determination can be made (by the communicationsdevice 102, 104, 106 and/or the interface server 218) regarding theactions that may be implemented to achieve the desired outcome. Once thecommand, command assignment and interface actions are set, the user caninput the command to the communications device 102, 104, 106 to initiatethe desired actions.

One should note that the above nonlimiting example may be implementedvia a graphical user interface, an audio interface, and/or may bepre-configured by the communications device 102, 104, 106. Additionally,while at least a portion of the logic may reside at the communicationsdevice 102, 104, 106, this is also a nonlimiting example. In at leastone exemplary embodiment at least a portion of the logic may reside atthe interface server 218.

One should also note that, while some embodiments may include logic inthe communications device 102, 104, 106 for receiving a marker, auralthumbnail, etc. and navigating an information tree, these arenonlimiting examples. More specifically, in at least one configuration,the interface server 218 and associated IVR may include logic forfacilitating the capture and presentation of the thumbnail, marker,and/or command to perform the desired actions.

As discussed above, some embodiments may be configured such thatcommunications device 102, 104, 106 includes logic for facilitatingassociation of the image, audio, and/or video data with an IVR. As such,some embodiments may be configured to provide one or more of the optionsdiscussed in FIGS. 5-8 prior to (or during) interaction with the IVR.Selection of options from FIGS. 5-8 may be made via a “point and click”interaction with a GUI, via a predetermined key sequence, and/or othertechniques for selection.

FIG. 9 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for navigating an IVR, such as may be provided bythe interface server 218 from FIG. 4. As illustrated in the nonlimitingexample of FIG. 9, the communications device 102, 104, 106 canfacilitate a communication to an interface, such as an information tree(block 932). The communications device 102, 104, 106 can receive aprompt from the interface server 218 and communicate the prompt to theuser (block 934). The communications device 102, 104, 106 can thenreceive user input related to navigating the interface (block 936). Thecommunications device 102, 104, 106 can send at least a portion of thereceived input to the interface server 218 (block 938). Thecommunications device 102, 104, 106 can determine whether thecommunications session has ended (block 940). If not, the flowchartreturns to block 934. If the communications session has ended, theprocess may end.

FIG. 10 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for creating a marker for an IVR, similar to theflowchart from FIG. 9. As illustrated in the nonlimiting example of FIG.10, the communications device 102, 104, 106 can receive an indication tocreate a marker (block 1032). The communications device 102, 104, 106can determine the marker type and capture the marker (block 1034). Thecommunications device 102, 104, 106 can facilitate a communication withthe interface server 218 (block 1036). The communications device 102,104, 106 can receive a marker from the user and can record the user'sposition with respect to an information tree provided by the interfaceserver 218 (block 1038).

FIG. 11 is a flowchart illustrating an exemplary embodiment of a processthat may be utilized for resuming an IVR session, similar to theflowchart from FIG. 10. As illustrated in the nonlimiting example ofFIG. 11, the communications device 102, 104, 106 can initiate acommunication with the interface server 218 (block 1132). Thecommunications device 102, 104, 106 can receive user input related toresuming a previous position according to a previously captured marker(block 1134). The communications device 102, 104, 106 can access datarelated to the marker (block 1136). The communications device 102, 104,106 can automatically navigate the IVR to return to the stored position(block 1138).

One should note that while, in some embodiments the interface server 218may include logic for automatically taking the user back to the markedposition, in this nonlimiting example, the communications device 102,104, 106 includes logic to automatically navigate the information treeto reach the desired location. The navigation can include one or moreDual Tone Multi-Frequency (DTMF), voice commands, and/or other commandsthat are stored on the communications device 102, 104, 106. Thecommunications device 102, 104, 106 can then send the command(s) to theinterface server 218 to navigate to the desired position.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a processfor receiving a command and command assignment for implementation in anIVR session, similar to the flowchart from FIG. 11. As illustrated inthe nonlimiting example of FIG. 12, the communications device 102, 104,106 can receive an indication to create an interface command and acommand assignment (block 1232). The communications device 102, 104, 106can then determine the command that will be associated with the commandassignment (block 1234). The communications device 102, 104, 106 canthen determine a command assignment that will be associated with thedetermined command (block 1236). The communications device 102, 104, 106can store the received command and command assignment (block 1238).

As indicated above, in at least one exemplary embodiment, the user candefine commands that can be assigned to IVR actions. More specifically,a user can assign a sound, image, video, etc. to signify an action whenthe user interacts with the IVR.

FIG. 13 is a flowchart illustrating an exemplary embodiment of a processfor utilizing a command and command assignment in an IVR session,similar to the flowchart from FIG. 12. As illustrated in the nonlimitingexample of FIG. 13, the communications device 102, 104, 106 can initiatea communication with the interface server 218 (block 1332). Thecommunications device 102, 104, 106 can receive and interpret at leastone interface server action (block 1334).

The communications device 102, 104, 106 can associate the interfaceactions with a command and command assignment (block 1336) Thecommunications device 102, 104, 106 can receive a command from the user,the command being associated with the IVR (block 1338). Thecommunications device 102, 104, 106 can convert the command into aninterface action according to a previously configured command assignment(block 1340). As discussed above, the communications device 102, 104,106 can be configured with a command and command assignment to provideIVR navigation options for the user. While the command and commandassignments may be configured by the user, this is not a requirement, asin at least one exemplary embodiment the communications device 102, 104,106 can be configured with commands and command assignments without userinput.

The communications device 102, 104, 106 can be configured to convert thecommand into an interface action according to the command assignment(block 1340). The communications device 102, 104, 106 can then send theinterface action to the interface server 218 (block 1342).

FIG. 14 is a flowchart illustrating an exemplary embodiment of a processfor returning a user to a desired point in an IVR menu, similar to theflowchart from FIG. 13. As illustrated in the nonlimiting example ofFIG. 14, the communications device 102, 104, 106 can facilitatecommunications with the interface server 218 (block 1432). Thecommunications device 102, 104, 106 can receive data from the interfaceserver 218 (block 1434). The communications device 102, 104, 106 canrecord the received data (block 1436). The communications device 102,104, 106 can provide the received data to the user (block 1438). Thecommunications device 102, 104, 106 can receive a user indication tomark the current position in the information tree (block 1440). Thecommunications device 102, 104, 106 can record the user response (block1442). The communications device 102, 104, 106 can then determinewhether the received user input includes an instruction to proceed to adifferent point in the information tree, as described above (block1444). If the received user response is not a “take me” input (asdescribed above), the flowchart can return to block 1436. If thereceived response is a “take me” input, the communications device canreturn the user to the requested point in the information tree (block1446).

FIG. 15 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to provide an IVR session to a user, similar tothe flowchart from FIG. 14. As illustrated in the nonlimiting example ofFIG. 15, the interface server 218 can facilitate a communication withthe user device 102, 104, 106 (block 1532). The interface server 218 canthen provide a prompt for the user (block 1534). The interface server218 can receive a response from the user (block 1536). The interfaceserver 218 can provide additional information to the user (block 1538).The interface server 218 can then determine whether the communicationhas ended (block 1540). If not, the flowchart returns to block 1534.

FIG. 16A is a flowchart illustrating an exemplary embodiment of aprocess for an interface server to record a user position during an IVRsession, similar to the flowchart from FIG. 15. As illustrated in thenonlimiting example of FIG. 16A, the interface server 218 can facilitatea communication with a user (block 1632). The interface server 218 canreceive identification data associated with the communication device102, 104, 106 (block 1634). The interface server 218 can provide aprompt to the user (block 1636). The interface server 218 can receive aresponse from the user (block 1638). The interface server 218 can thenprovide information to the user (block 1640). The interface server 218can record a user position in the information tree (block 1642). Theinterface server 218 can determine whether the communication has ended(block 1644). If not, the flowchart returns to block 1636. If thecommunication has ended, the flowchart proceeds to jump block 1646.

FIG. 16B is a continuation of the flowchart from FIG. 16A. Morespecifically, from jump block 1648, the interface server 218 canfacilitate a new communication with the user (block 1650). The interfaceserver 218 can receive identification information from the user (block1652). The information can include callerID information, IP addressinformation, and/or other authenticating information. The interfaceserver 218 can then provide an option to resume a previous communication(block 1654). If the user desires to resume a previous communication,the interface server 218 can determine the previously stored position inthe information tree and return the user to that location.

FIG. 17 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to receive a command and command assignment,similar to the flowchart from FIGS. 16A and 16B. As illustrated in thenonlimiting example of FIG. 17, the interface server 218 can facilitatea communication with a user (block 1732). The interface server 218 canreceive identification data associated with a user communication device(block 1734). The interface server 218 can provide a user option todetermine at least one command and command assignment (block 1736). Theinterface server 218 can receive a command assignment and associatedcommand from the user (block 1738). The interface server 218 can storethe command assignment and associated command (block 1740). As discussedabove, a determination may also be made as to the one or more actions toachieve the desired result associated with the command and commandassignment.

FIG. 18 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to execute a desired command according to acommand assignment, similar to the flowchart from FIG. 19. Asillustrated in the nonlimiting example of FIG. 18, the interface server218 can facilitate a communication with the user (block 1832). Theinterface server 218 can provide data to the user (block 1834). Asdiscussed above, the data provided to the user can include dataassociated with an information tree. The interface server 218 can thenreceive a command from the user (block 1836). The interface server 218can determine a command assignment associated with the received command(block 1838). The interface server 218 can execute the desired actionaccording to the command assignment (block 1840).

FIG. 19 is a flowchart illustrating an exemplary embodiment of a processfor an interface server to return a user to a desired point in an IVR,similar to the flowchart from FIG. 18. As illustrated in the nonlimitingexample of FIG. 19, the interface server 218 can facilitate acommunication with a user (block 1932). The interface server 218 canreceive identification information from the communications device 102,104, 106 (block 1934). The interface server 218 can provide data to thecommunications device 102, 104, 106 (block 1936). The interface server218 can record data provided to the communications device 102, 104, 106(block 1938). The interface server 218 can receive a user response(block 1940). The interface server 218 can record the received userresponse (block 1942). The interface server 218 can then determinewhether “take me” input has been received from the user (block 1944). Ifno such input has been received, the flowchart returns to block 1936. If“take me” input has been received, as indicated above, the interfaceserver 1946 can return the user to the requested point in the IVR (block1946)

FIG. 20A is a sequence diagram illustrating an exemplary embodiment of aprocess for providing a setting for an IVR, such as may be provided bythe interface server 218 from FIG. 3. As illustrated in the nonlimitingexample of FIG. 20A, the user can initiate activation of thecommunications device 102, 104, 106 (arrow 2032). The communicationsdevice 102, 104, 106 can provide an option to define at least onecommand and/or command setting (arrow 2034). The user can define atleast one command and/or command setting (arrow 2036). The user caninitiate a communication with the interface server 218 (arrow 2038). Thecommunications device 102, 104, 106 can connect with the interfaceserver 218 (arrow 2040). The communications device 102, 104, 106 canprovide identification information, the command and/or the commandsetting to the interface server 218 (arrow 2042).

FIG. 20B is a continuation of the sequence diagram from FIG. 20A. Morespecifically, continuing from FIG. 20A, the interface server 218 canprovide data and/or a user prompt (arrow 2044). The communicationsdevice 102, 104, 106 can provide the option to the user (arrow 2046).The user can respond to the option with the command (arrow 2048). Thecommunications device 102, 104, 106 can send the command to theinterface server 218 (arrow 2050). The interface server 218 determinesactions that may be utilized according to the command and executes theactions accordingly (arrow 2052). The communication can then beterminated (arrow 2054).

The embodiments disclosed herein can be implemented in hardware,software, firmware, or a combination thereof. At least one embodiment,disclosed herein is implemented in software and/or firmware that isstored in a memory and that is executed by a suitable instructionexecution system. If implemented in hardware, as in an alternativeembodiment embodiments disclosed herein can be implemented with any or acombination of the following technologies: a discrete logic circuit(s)having logic gates for implementing logic functions upon data signals,an application specific integrated circuit (ASIC) having appropriatecombinational logic gates, a programmable gate array(s) (PGA), a fieldprogrammable gate array (FPGA), etc.

One should note that the flowcharts included herein show thearchitecture, functionality, and operation of a possible implementationof software. In this regard, each block can be interpreted to representa module, segment, or portion of code, which comprises one or moreexecutable instructions for implementing the specified logicalfunction(s). It should also be noted that in some alternativeimplementations, the functions noted in the blocks may occur out of theorder and/or not at all. For example, two blocks shown in succession mayin fact be executed substantially concurrently or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved.

One should note that any of the programs listed herein, which caninclude an ordered listing of executable instructions for implementinglogical functions, can be embodied in any computer-readable medium foruse by or in connection with an instruction execution system, apparatus,or device, such as a computer-based system, processor-containing system,or other system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “computer-readable medium” can be anymeans that can contain, store, communicate, or transport the program foruse by or in connection with the instruction execution system,apparatus, or device. The computer readable medium can be, for examplebut not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device. More specificexamples (a nonexhaustive list) of the computer-readable medium couldinclude an electrical connection (electronic) having one or more wires,a portable computer diskette (magnetic), a random access memory (RAM)(electronic), a read-only memory (ROM) (electronic), an erasableprogrammable read-only memory (EPROM or Flash memory) (electronic), anoptical fiber (optical), and a portable compact disc read-only memory(CDROM) (optical). In addition, the scope of the certain embodiments ofthis disclosure can include embodying the functionality described inlogic embodied in hardware or software-configured mediums.

One should also note that conditional language, such as, among others,“can,” “could,” “might,” or “may,” unless specifically stated otherwise,or otherwise understood within the context as used, is generallyintended to convey that certain embodiments include, while otherembodiments do not include, certain features, elements and/or steps.Thus, such conditional language is not generally intended to imply thatfeatures, elements and/or steps are in any way required for one or moreparticular embodiments or that one or more particular embodimentsnecessarily include logic for deciding, with or without user input orprompting, whether these features, elements and/or steps are included orare to be performed in any particular embodiment.

It should be emphasized that the above-described embodiments are merelypossible examples of implementations, merely set forth for a clearunderstanding of the principles of this disclosure. Many variations andmodifications may be made to the above-described embodiment(s) withoutdeparting substantially from the spirit and principles of thedisclosure. All such modifications and variations are intended to beincluded herein within the scope of this disclosure.

therefore, at least the following is claimed:
 1. A method, comprising: prompting a user to provide a marker to be associated with a particular position in an information tree; receiving a version of the marker from the user; and associating the version of the marker received from the user with the particular position in the information tree and storing the particular position in the information tree associated with the version of the marker, wherein a subsequent input of a new version of the marker by the user causes a server to navigate to the particular position in the information tree that has been stored and associated with a prior version of the marker received from the user.
 2. The method of claim 1, wherein the marker includes at least one of the following: audio data, image data, control data, and video data.
 3. The method of claim 1, further comprising directing the user to the particular position in the information tree that is associated with the marker.
 4. The method of claim 1, further comprising determining the marker that is configured to mark the particular position in the information tree.
 5. The method of claim 4, wherein determining the marker includes at least one of the following: capturing audio data, capturing image data, capturing video data, finding audio data, finding image data, and finding video data.
 6. The method of claim 1, wherein receiving the version of the marker from the user further comprises capturing an audio recording of at least one word spoken by the user.
 7. The method of claim 6, wherein the subsequent input of the new version of the marker comprises the user speaking the at least one word at a subsequent time after the audio recording is captured.
 8. A non-transitory computer readable medium having a computer program with instructions, when executed by a computer, cause the computer to: prompt a user to provide a marker to be associated with a particular position in an information tree; receive a version of the marker from the user; and associate the version of the marker received from the user with the particular position in the information tree and store the particular position in the information tree associated with the version of the marker, wherein a subsequent input of a new version of the marker by the user causes a server to navigate to the particular position in the information tree that has been stored and associated with a prior version of the marker received from the user.
 9. The non-transitory computer readable medium of claim 8, wherein the marker includes at least one of the following: audio data, image data, control data, and video data.
 10. The non-transitory computer readable medium of claim 8, the instructions further causing the computer to direct the user to the particular position in the information tree that is associated with the marker.
 11. The non-transitory computer readable medium of claim 8, the instructions further causing the computer to determine the marker that is configured to mark the particular position in the information tree.
 12. The non-transitory computer readable medium of claim 11, wherein determining the marker includes at least one of the following: capturing audio data, capturing image data, capturing video data, finding audio data, finding image data, and finding video data.
 13. The non-transitory computer readable medium of claim 8, wherein receiving the version of the marker from the user further comprises capturing an audio recording of at least one word spoken by the user.
 14. The non-transitory computer readable medium of claim 13, wherein the subsequent input of the new version of the marker comprises the user speaking the at least one word at a subsequent time after the audio recording is captured.
 15. A server, comprising: a computer processor; and at least one memory comprising instructions that cause the computer processor, when executed, to: prompt a user to provide a marker to be associated with a particular position in an information tree; receive a version of the marker from the user; and associate the version of the marker received from the user with the particular position in the information tree and store the particular position in the information tree associated with the version of the marker, wherein a subsequent input of a new version of the marker by the user causes the server to navigate to the particular position in the information tree that has been stored and associated with a prior version of the marker received from the user.
 16. The server of claim 15, wherein the marker includes at least one of the following: audio data, image data, control data, and video data.
 17. The server of claim 15, the instructions further causing the computer processor to direct the user to the particular position in the information tree that is associated with the marker.
 18. The server of claim 15, the instructions further causing the computer processor to determine the marker that is configured to mark the particular position in the information tree.
 19. The server of claim 18, wherein determining the marker includes at least one of the following: capturing audio data, capturing image data, capturing video data, finding audio data, finding image data, and finding video data.
 20. The server of claim 15, wherein receiving the version of the marker from the user further comprises capturing an audio recording of at least one word spoken by the user. 